This test ensures that stack traces map correctly to source files and that coverage reports are generated when running Vitest in browser mode with coverage enabled. This provides validation for the current implementation and will help verify future refactors removing the source-map-support dependency.

This change removes the injection of `source-map-support` in Vitest browser tests and enables sourcemap rebasing for coverage runs as well. This allows Vitest's native remapper to handle stack traces and coverage correctly without needing the external polyfill in the browser. The E2E tests have been verified to pass with these changes. The unused `createSourcemapSupportPlugin` function has also been removed.

See associated pull request for more information.

See associated pull request for more information.

Adds a new schematic migration to automatically add trustProxyHeaders configuration to server.ts files in workspaces where either AngularNodeAppEngine or AngularAppEngine are used.

…base rule

Remove the `find_examples` tool from the Angular CLI MCP server, along with the `ng_examples_db`
Bazel rule and associated example files. With the availability of the official Angular developer
skills repository (https://github.com/angular/skills), this local database lookup tool is redundant.
Reduce maintenance overhead and simplify the codebase by eliminating the need to maintain a local
SQLite database of examples within the CLI repository.

See associated pull request for more information.

See associated pull request for more information.

This should have been done by the release process but it failed.

…r usage

Removes the last usage of `createConsoleLogger` in the repository from
the webpack builder tests. This makes the test consistent with others
in the file and allows for potential removal of the function.

Also removes an unused `BuildResult` import in the same file.

`createConsoleLogger` is deprecated. Use a custom logger implementation instead. This does not apply to application code.

See associated pull request for more information.

See associated pull request for more information.

…eaders is true

Previously, setting `trustProxyHeaders: true` only allowed a predefined set of common proxy headers (such as `x-forwarded-for` and `x-forwarded-host`). This resulted in warning logs when requests contained other valid proxy headers like `x-forwarded-client-cert` or `x-forwarded-email`.

…ureSupport

The `target` parameter in the `getFeatureSupport` function is no longer used internally, so it has been removed to simplify the function signature and call sites.

…f rendering implementation details

Unlike ng_package doesn't add these fields.

Virtual files generated by esbuild for disabled browser fields leak into the
watch list, causing spurious rebuilds in watch mode.

Previously, only paths where the suffix was a Node.js builtin module were
ignored. Now, any path containing `(disabled):` is ignored as it represents
a virtual file that doesn't exist on disk.

Fixes #33160

…istry.ts

…actor-jasmine-vitest

The `refactor-jasmine-vitest` schematic fails to remove `.args` when migrating
`spy.calls.all()[i].args`, resulting in uncompilable code in Vitest.

Now, a specialized transformer detects `spy.calls.all()[i].args` and transforms
it to `vi.mocked(spy).mock.calls[i]`, removing the unnecessary `.args` property
access.

Fixes #33112